-
Couldn't load subscription status.
- Fork 47
Admin API guide #1390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin API guide #1390
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nice work
|
|
||
| Most Admin API operations are also available using xref:get-started:intro-to-rpk.adoc[`rpk`], a CLI tool which interacts with the Admin API under the hood. | ||
|
|
||
| Redpanda version 25.3 introduces a version 2 of the Admin API, powered by https://connectrpc.com/docs/introduction[ConnectRPC]. New Redpanda features and operations introduced starting in version 25.3 are available with Admin API v2 only, and are not backported to Admin API v1. Supported Admin API v1 operations remain available and you can continue to use them per usual (including with rpk v25.3 and later). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I keep seeing v25.3 in other contexts. No big deal, but we should all be on the same page wrt how we do this.
|
|
||
| Most Admin API operations are also available using xref:get-started:intro-to-rpk.adoc[`rpk`], a CLI tool which interacts with the Admin API under the hood. | ||
|
|
||
| Redpanda version 25.3 introduces a version 2 of the Admin API, powered by https://connectrpc.com/docs/introduction[ConnectRPC]. New Redpanda features and operations introduced starting in version 25.3 are available with Admin API v2 only, and are not backported to Admin API v1. Supported Admin API v1 operations remain available and you can continue to use them per usual (including with rpk v25.3 and later). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Redpanda version 25.3 introduces a version 2 of the Admin API, powered by https://connectrpc.com/docs/introduction[ConnectRPC]. New Redpanda features and operations introduced starting in version 25.3 are available with Admin API v2 only, and are not backported to Admin API v1. Supported Admin API v1 operations remain available and you can continue to use them per usual (including with rpk v25.3 and later). | |
| Redpanda v25.3 introduces a version 2 of the Admin API, powered by https://connectrpc.com/docs/introduction[ConnectRPC]. New Redpanda features and operations introduced in version 25.3 are available with Admin API v2 only, and are not backported to Admin API v1. Supported Admin API v1 operations remain available and you can continue to use them as usual (including with rpk v25.3 and later). |
| ** For Admin API v1, any supported version of Redpanda. For Admin API v2, Redpanda version 25.3 or later. | ||
| * Superuser privileges, if xref:manage:security/authentication.adoc#enable-authentication[authentication] is enabled on your cluster for the Admin API. For more information, see xref:manage:security/authentication.adoc#create-superusers[Configure Authentication]. (Some endpoints are read-only and do not require superuser access.) | ||
| * A tool to make HTTP requests, such as `curl`, or client libraries for your programming language of choice. | ||
| ** For Admin API v2, you can also make requests using a Connect client. You can install the Connect plugin for your preferred language and use the Protobuf compiler to generate an SDK. Admin API v2 is also available as a Buf module and can be accessed through the https://buf.build/redpandadata/core/docs/dev:redpanda.core.admin.v2[Buf Schema Registry]. The https://buf.build/docs/cli/[Buf CLI] provides an easy way to generate client SDKs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a Kafka Connect? If you are referring generally to connectors, wouldn't this be "connect"?
Or is this Redpanda Connect?
| ** For Admin API v1, any supported version of Redpanda. For Admin API v2, Redpanda version 25.3 or later. | ||
| * Superuser privileges, if xref:manage:security/authentication.adoc#enable-authentication[authentication] is enabled on your cluster for the Admin API. For more information, see xref:manage:security/authentication.adoc#create-superusers[Configure Authentication]. (Some endpoints are read-only and do not require superuser access.) | ||
| * A tool to make HTTP requests, such as `curl`, or client libraries for your programming language of choice. | ||
| ** For Admin API v2, you can also make requests using a Connect client. You can install the Connect plugin for your preferred language and use the Protobuf compiler to generate an SDK. Admin API v2 is also available as a Buf module and can be accessed through the https://buf.build/redpandadata/core/docs/dev:redpanda.core.admin.v2[Buf Schema Registry]. The https://buf.build/docs/cli/[Buf CLI] provides an easy way to generate client SDKs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ** For Admin API v2, you can also make requests using a Connect client. You can install the Connect plugin for your preferred language and use the Protobuf compiler to generate an SDK. Admin API v2 is also available as a Buf module and can be accessed through the https://buf.build/redpandadata/core/docs/dev:redpanda.core.admin.v2[Buf Schema Registry]. The https://buf.build/docs/cli/[Buf CLI] provides an easy way to generate client SDKs. | |
| ** For Admin API v2, you can also make requests using a Connect client. You can install the Connect plugin for your preferred language and use the Protobuf compiler to generate an SDK. Admin API v2 is also available as a Buf module, which you can access using the https://buf.build/redpandadata/core/docs/dev:redpanda.core.admin.v2[Buf Schema Registry]. The https://buf.build/docs/cli/[Buf CLI] provides an easy way to generate client SDKs. |
|
|
||
| == Choose an Admin API version | ||
|
|
||
| In Redpanda version 25.3, Admin API v2 endpoints are entirely exclusive to v2, and there is virtually no overlap in functionality between v2 and v1. You can use both versions of the Admin API on the same cluster, so choosing which version depends on whether you use the following v2-only features: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not mix v and version, especially in the same paragraph
|
|
||
| == Choose an Admin API version | ||
|
|
||
| In Redpanda version 25.3, Admin API v2 endpoints are entirely exclusive to v2, and there is virtually no overlap in functionality between v2 and v1. You can use both versions of the Admin API on the same cluster, so choosing which version depends on whether you use the following v2-only features: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| In Redpanda version 25.3, Admin API v2 endpoints are entirely exclusive to v2, and there is virtually no overlap in functionality between v2 and v1. You can use both versions of the Admin API on the same cluster, so choosing which version depends on whether you use the following v2-only features: | |
| In Redpanda v25.3, Admin API v2 endpoints are entirely exclusive to v2, and there is virtually no overlap in functionality between v2 and v1. You can use both versions of the Admin API on the same cluster, so choosing which version depends on whether you use the following v2-only features: |
|
|
||
| === Use Admin API v2 | ||
|
|
||
| The Admin API v2 is built on ConnectRPC, so you can send `curl` requests with a JSON payload, or use a generated Connect client to call the same methods directly from your application code. The v2 paths are the fully qualified names of the services. All v2 endpoints accept POST requests only. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Connect client<--- Redpanda Connect? Kafka Connect? connect client?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See suggested updates
|
@mattschumpert Do we want to announce Admin v2 in What's New? |
Co-authored-by: Joyce Fee <[email protected]>
8b20de2 to
2d1adde
Compare
|
|
||
| Most Admin API operations are also available using xref:get-started:intro-to-rpk.adoc[`rpk`], a CLI tool that interacts with the Admin API under the hood. | ||
|
|
||
| Redpanda v25.3 introduces new endpoints to the Admin API that are served with https://connectrpc.com/docs/introduction[ConnectRPC]. New Redpanda features and operations available starting in v25.3 are accessible as RPC services through these new endpoints. Existing Admin API operations from versions earlier than 25.3 remain available at the same URLs and you can continue to use them as usual (including with rpk v25.3 and later). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...remain available at the same URLs...
The same URLs as what?
| == Prerequisites | ||
|
|
||
| * A running Redpanda Self-Managed cluster. | ||
| * Superuser privileges, if xref:manage:security/authentication.adoc#enable-authentication[authentication] is enabled on your cluster for the Admin API. For more information, see xref:manage:security/authentication.adoc#create-superusers[Configure Authentication]. (Some endpoints are read-only and do not require superuser access.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So if I want to know if the endpoints I need to use require superuser access, can I view a list somewhere that tells me which endpoints require it and which ones don't?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All v2 endpoints require superuser, but I don't have a definitive list for v1. Will reach out to an SME - if this list can be put together, these details can be added at a later time
| ``` | ||
|
|
||
| // TODO: Update link if necessary when v2 URLs are finalized | ||
| For a full list of available endpoints, see the link:/api/doc/admin/[Admin API Reference]. Select "v1" in the version selector to view legacy endpoints. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
link to the Admin API Reference does not render in html output - throws a Page Not Found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a limitation with our Bump-hosted (link:/) pages, they don't get included in the preview build
| -- | ||
| ==== | ||
|
|
||
| === Use new (ConnectRPC) endpoints |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe consider: Use ConnectRPC endpoints
and then put a note explaining what makes them different from v1 endpoints.
| * Shadowing | ||
| * Connected client monitoring | ||
|
|
||
| For a full list of available endpoints, see the link:/api/doc/admin/v2/[Admin API Reference]. Select "v2" in the version selector to view the ConnectRPC endpoints. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattschumpert I think users are going to be throwing questions our way--we should be up front/transparent about v1 vs v2. If we are not, this will generate questions and may undermine user confidence in the docs.
Co-authored-by: Joyce Fee <[email protected]>
Description
This pull request introduces documentation for the new ConnectRPC-powered Admin API endpoints in Redpanda v25.3 and updates navigation and references throughout the docs to surface these changes. The most important changes are the addition of a dedicated Admin API usage guide, updates to the release notes to announce the new endpoints, and improved navigation and reference structure to distinguish between legacy and new Admin API endpoints.
Admin API documentation and navigation improvements:
use-admin-api.adoc, providing a comprehensive guide on managing Redpanda clusters using both legacy and new ConnectRPC Admin API endpoints, including usage examples and authentication details.nav.adocto add direct links to the new Admin API usage guide and the ConnectRPC Admin API reference, making it easier for users to find relevant documentation. [1] [2]v1) and new ConnectRPC (v2) Admin API endpoints, including versioning details and links to the new usage guide.Release notes updates:
These changes collectively improve discoverability, clarity, and usability of the Admin API documentation for both new and existing Redpanda users.
Resolves https://redpandadata.atlassian.net/browse/
Review deadline: 16 Oct
Page previews
Manage > Manage Redpanda Using the Admin API
Reference > API Reference
What's New
Checks